System and method for synchronizing camera footage from a plurality of cameras in canvassing a scene

ABSTRACT

A method for synchronizing camera footage from a plurality of cameras includes automatically identifying cameras relevant to an incident that occurs at a predetermined date and time based on a location of the incident and on cameras&#39; locations stored in a database. A correction is associated with each camera that is based on a difference between the camera&#39;s metadata observed at an actual date/time. Methods are employed to reduce human error. The correction may be applied to the predetermined date and time simultaneously for the plurality of cameras to generate an adjusted date/time in metadata for synchronizing camera footage to the incident time. A list of the identified cameras may be exported and associated with a case number or User ID. The list may include camera locations, the adjusted metadata to synchronize the cameras, and bases for the correction calculation. The list is optionally generated via mapping functions.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of and priority to U.S. ProvisionalApplication Ser. No. 62/325,731, filed Apr. 21, 2016, entitled “CameraCanvass Tracker,” the entirety of which is hereby incorporated herein byreference thereto.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to investigations, such as lawenforcement investigations, using cameras to help canvass a scene and,in particular, to a method and system for synchronizing camera footagefrom a plurality of cameras in canvassing a scene.

BACKGROUND

As the use of surveillance cameras by law enforcement agencies hascontinued to grow in the fight against crime and terrorism, severalproblems have been recognized by those tasked to gather video data.Among these problems are inaccuracies in the metadata, particularly, thetime of day, and/or the calendar day, that is recorded with the camerasurveillance video.

Such errors can easily occur in cameras that still rely on manually setdates and times, and which may have been inaccurately entered. Moreover,even cameras which were initialized manually with accurate calendar dayand time entries, or even those which were initialized automatically bysynchronizing with satellite data may have failed to properly resetafter a power outage or may be “off” due to errors that may occur due todaylight savings time cycles. As a result, such metadata may notaccurately represent the date and time when the surveillance footage ofa crime scene, for example, was actually recorded.

For example, an investigator wishes to view surveillance video on acamera that could have captured an event of interest. Upon inspectingthe camera of interest, the investigator finds that, although thecurrent date and time is actually 3:09 PM, Mar. 11, 2016, the video thecamera is currently recording is time-stamped as 10:17 PM, Mar. 9, 2016.The time on the camera is off by one day, plus 16 hours and 52 minutes.The investigator would need to correct for this error to correctlylocate the recorded footage on the camera corresponding to the actualtime the event occurred. If, for example, an incident occurred on Mar.3, 2016 at 12:11 PM, the investigator would need to turn this camera toMar. 1, 2016 at 7:19 PM to view the incident (if captured) on thiscamera.

Such calculations involving date and time, however, are difficult andtime consuming, lend themselves to human error. In particular, they areperformed over and over again for the same camera on each occasion thecamera is examined by an investigator, and on multiple cameras during aninvestigation, that need to be cued to the same actual date and time.This is extremely time-consuming, subject to human error, and can leadto questions about the veracity of the video evidence acquired. There isa particular need, therefore, for investigators to quickly locate andobtain footage from any camera that may have captured relevantinformation, which can then be accurately and quickly synchronized to atime coinciding with an incident under investigation. In addition,because the camera footage and related information may become evidenceat trial, it is also essential to document and track the acquisition andanalysis of the camera footage, including documenting the basis andaccuracy of the calculations to reliably authenticate the actual timethat the camera footage corresponds to.

There is a need, therefore, for an incident time calculator tosynchronize a camera's date and time metadata with actual, correct datato quickly locate video footage of interest, and to do so for aplurality of cameras that may capture relevant footage of a crime scene,for example.

SUMMARY

The present disclosure is directed to a method and system forsynchronizing a camera's date and time metadata with actual, correctdata to quickly locate video footage of interest on the camera. Thepresent disclosure is also directed to a method for quickly locating aplurality of cameras that may have viewed activity relevant to anincident under investigation and synchronizing video camera recordingsfrom the plurality of cameras.

The present disclosure is also directed to a method for synchronizingcamera footage from a plurality of cameras, which includes identifying,by a processing device, a plurality of cameras associated with anincident that occurred at a predetermined date and time, based on alocation of each of the plurality of cameras, and associating each ofthe plurality of cameras with a correction to a date and time inmetadata associated with footage recorded by the corresponding camera tosynchronize the footage recorded by each of the plurality of cameras toan actual date and time. The method further includes applying thecorrection, by the processing device, associated with each of theplurality of cameras to determine an adjusted date and time in themetadata for each camera that corresponds to footage recorded at thepredetermined date and time of the incident.

The present disclosure is also directed to a method for synchronizingcamera footage from a plurality of cameras, which includes identifying,by a processing device, from a database of cameras, a plurality ofcameras associated with an incident, based at least on a location ofeach of the plurality of cameras, and associating each of the pluralityof cameras with a correction to at least one of a date and a time inmetadata associated with footage recorded by the corresponding camera tofacilitate synchronization of the footage recorded by each of theplurality of cameras to an actual date and time, and storing thecorrection to the metadata for each of the plurality of cameras in thedatabase. The method further includes applying, by the processingdevice, the correction stored in the database associated with each ofthe plurality of cameras to determine at least one of an adjusted dateand an adjusted time in the metadata for each camera that corresponds tofootage recorded at a particular date and time related to the incident.The method further includes synchronizing the footage of each of theplurality of cameras to the particular date and time, including cueingthe footage of each of the plurality of cameras to the particular dateand time based on the at least one of the adjusted date and the adjustedtime determined from the correction to the metadata stored in thedatabase for each of the plurality of cameras.

In aspects, the correction to the metadata stored in the database can beapplied simultaneously for each of the plurality of cameras.

In additional aspects, a new particular date and time may be entered viaa user device operatively connected to the processing device and thecorrection saved in the database simultaneously applied to determine atleast one of a new adjusted date and a new adjusted time for one of theplurality of cameras.

In one aspect, the method further includes generating, by the processingdevice, a list of the plurality of cameras identified from theidentifying step, and exporting, by the processing device, the list to afile and/or an email account associated with a user ID. The listpreferably includes the location, the correction, and the at least oneof the adjusted date and the adjusted time in the metadata associatedwith each of the plurality of cameras.

The method may further include associating, by the processing device,the list with at least one of a case number, a user ID, and a groupassociated with the user ID.

In another aspect, the method further includes receiving and storing, bya processing device, details of cameras in a database. The camerasstored in the database include the plurality of cameras that areidentified based on their location. The plurality of cameras areidentified from location details based on their location relative to anincident location at which the incident occurred. The details stored inthe database for each camera include location details, including ageographical location associated with each camera in the database.

The details received and stored for one camera in the database ofcameras include the actual date and time and at least one of an observeddate and an observed time in the metadata coinciding with the actualdate and time, wherein the at least one of the observed date and theobserved time are received via user input to a user device operativelyconnected to the database.

In various aspects, the details of each of the cameras in the databasefurther include at least one of a camera operable indicator, contactinformation, a make and model of the corresponding camera, a date thecorresponding camera was entered into the database, and a date thecorresponding camera was last synchronized.

In aspects, the method further includes calculating, for the one camerain the database, the correction to the metadata to synchronize thefootage based on the at least one of the observed date and the observedtime recorded by the one camera coinciding with the actual date and timethat the metadata (date and time) are recorded. The method furtherincludes associating the one camera in the database of cameras with thecorresponding correction and storing the corresponding correction in thedatabase.

In additional aspects, the actual date and time for the one camera maybe automatically imported via the user device from one of a cellularnetwork and a GPS date/time stamp coinciding with the observed date andthe observed time in the metadata.

In additional aspects, the camera data may be received and stored in thedatabase via integrated mapping functions. In one aspect, the method mayfurther include generating a map of an area that includes the incidentlocation, and displaying it on a user device operatively connected tothe database. The method also includes indicating the incident locationon the map with a first graphical element; and populating the map with aplurality of second graphical elements indicating the geographicallocation of each camera from the database within a selected area aroundthe first graphical element. Each camera located within the selectedarea corresponds to one of the plurality of cameras that is identifiedas potentially relevant, based on its location.

In aspects, the method further includes generating a list of theplurality of cameras using the plurality of second graphical elementswithin the selected area. The list includes at least the location, thecorrection, and the at least one of the adjusted date and the adjustedtime in the metadata associated with each of the plurality of cameras.

In various aspects, the selected area may include the entire area of themap displayed on the user device; or a bounded region graphicallydefined by user input via the user device; or a bounded region definedby a user-defined distance from the incident location. All of theseoptions may be available to a user via a user device from which themethods are executed, based on the user's selection of the variousoptions.

The user, in aspects, may also fix the incident location on the map bydragging and dropping the first graphical element onto the map at theincident location.

In further aspects, the method may include selecting, via user input,one or more details associated with each of the plurality of cameras,and superimposing on the map the one or more details for at least one ofthe plurality of cameras.

The list may be filtered according to any of the details of the camerasstored in the database, and the filtered list may be graphicallyhighlighted on the map.

The present disclosure is further directed to a method that includescalculating a difference between a camera's metadata, particularly, thetime and date embedded with the video footage, and the actual, correcttime and date. The method further includes applying the calculateddifference to a date and time of an event of interest, to determine theembedded time and date of the video footage corresponding thereto, toassist a user in locating and viewing the corresponding video footage.

In aspects, the method may also include storing information associatedwith the camera in a database, including the location of the camera, thecalculated difference, and a date on which the calculated difference wasdetermined. A listing of the locations of the cameras for which detailsare entered are viewable by the user. A list and location, also viewableon a map, of cameras within a certain radius of an event can be quicklyaccessed.

The present disclosure is also directed to a method for synchronizingcamera footage from a plurality of cameras, the method includingidentifying, by a processing device, a plurality of cameras within apredetermined distance of an incident, wherein the incident occurs at apredicted, or known, date and time. The step of identifying includesautomatically identifying, by the processing device, the plurality ofcameras based on a location of the incident and on details of locationsof the plurality of cameras. The details of the plurality of cameras arepreferably stored in, and accessed from, a database that preferablyincludes details for cameras from a large geographical area, i.e.,including cameras not relevant to the incident or near the location ofthe incident being investigated. The method further includescalculating, by the processing device, for each of the plurality ofcameras, a difference between an actual date and time, which may bebased on data manually entered by a user or on an automaticallygenerated timestamp, and a recorded date and time, e.g., in metadata,associated with the corresponding camera. For each of the plurality ofcameras, the difference is applied, by the processing device, to thepredicted date and time to generate a new recorded date and timeassociated with the corresponding camera for locating and viewingfootage, recorded by the corresponding camera, at the predicted date andtime relevant to the incident. A list of the plurality of cameras isexported by the processing device. The list includes the location ofeach corresponding camera, and the new recorded date and time associatedtherewith, for locating and viewing footage relevant to the incident.

Other features and advantages will become apparent from the followingdescription of the preferred embodiments, taken in conjunction with theaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the disclosed system and method are describedherein with reference to the accompanying drawings, which form a part ofthis disclosure.

FIGS. 1-3 represent three consecutive screen shots (viewed by scrolling)of a so-called calculator screen viewed from a mobile device, such as amobile phone or tablet, executing a computer programming application(“app”) that implements embodiments of a method of the presentdisclosure.

FIGS. 4A-4C represent completed calculator screens FIGS. 1-3,respectively, after data is entered and the calculator is executed viathe app, the executed calculations shown in FIG. 4C.

FIG. 5 represents a fourth consecutive screen shot of the embodiment ofthe calculator screen.

FIGS. 6A-6C represent three consecutive screen shots (viewed byscrolling) of an embodiment of a DVR Details screen accessible via thecalculator screen of FIG. 5, for example.

FIGS. 7A-7C represent an example of completed DVR Details screen FIGS.6A-6C, respectively, after data is entered via the app.

FIG. 8 represents a screen shot of the saved DVR Details screen after auser selects the “Done” button, and a Menu screen selected from thesaved Details screen with additional options.

FIG. 9 represents a screen shot of a map view generated by the app.

FIGS. 10-12 represent screen shots of a DVR List screen generated by theapp.

FIG. 13 represents a screen shot of a map view showing locations ofDVR's generated by the app.

FIGS. 14-15 represent screens generated by the app for exporting DVRLists and reports.

FIG. 16 is an example of a report of a DVR List generated in accordancewith an embodiment of the present disclosure.

FIGS. 17-18 are representative user and DVR list screens, respectively,for use by an administrator of at least one group of users in accordancewith the embodiments.

FIG. 19 is a schematic diagram of an embodiment of a system of thepresent disclosure.

FIG. 20 is a functional block diagram of a user device configured toimplement embodiments of methods of the present disclosure.

FIG. 21 is a block diagram representation of embodiments of a method ofthe present disclosure.

FIG. 22 is a block diagram representation of additional embodiments of amethod of the present disclosure.

The various aspects of the present disclosure mentioned above aredescribed in further detail with reference to the aforementioned figuresand the following detailed description of exemplary embodiments.

DETAILED DESCRIPTION

Particular illustrative embodiments of the present disclosure aredescribed hereinbelow with reference to the accompanying drawings;however, the disclosed embodiments are merely examples of thedisclosure, which may be embodied in various forms. Well-known functionsor constructions and repetitive matter are not described in detail toavoid obscuring the present disclosure in unnecessary or redundantdetail. Therefore, specific structural and functional details disclosedherein are not to be interpreted as limiting, but merely as a basis forthe claims and as a representative basis for teaching one skilled in theart to variously employ the present disclosure in virtually anyappropriately detailed structure. In this description, as well as in thedrawings, like-referenced numbers represent elements which may performthe same, similar, or equivalent functions. The word “exemplary” is usedherein to mean “serving as an example, instance, or illustration.” Anyembodiment described herein as “exemplary” is not necessarily to beconstrued as preferred or advantageous over other embodiments. The word“example” may be used interchangeably with the term “exemplary.”

It is particularly advantageous to an investigator tasked withcanvassing of a crime scene or other incident to implement the functionsand methods of the disclosure for synchronizing video camera footage foruse on a mobile device. In the embodiments described herein, the methodsof the disclosure are implemented at least in part through modulesand/or computer programming applications, referred to as “apps,”installed and executed on a mobile device. It is understood, however,that the disclosure is not limited thereto.

In particular, as will be appreciated by one of ordinary skill in theart, aspects of the present disclosure may be embodied as a method, asystem, and/or a computer program product. Accordingly, aspects of thepresent disclosure may take the form of an entirely hardware embodiment,an entirely software embodiment, or an embodiment combining aspects ofboth hardware and software. Furthermore, the present disclosure may takethe form of a computer program product on a computer-readable storagemedium having computer-readable program code means embodied in thestorage medium. Any suitable computer-readable storage medium may beutilized, including volatile and non-volatile, removable andnon-removable media implemented in any method or technology for storageof information, such as computer readable instructions, data structures,program modules, or other data, and further including hard disks,CD-ROM, DVD-ROM, optical storage devices, magnetic storage devices,semiconductor memory storage devices (e.g., USB thumb drives, flashmemory or other memory technology) and/or the like, including RAM, ROM,and EEPROM, or any other medium which can be used to store informationand instructions which can be accessed by an application, module, and soon for execution by a processing device. Any such computer storage mediamay be part of the device or accessible or connectable thereto.

It should be noted that computer-readable storage medium, which may alsobe referred to as “non-transitory media,” refers to any tangible media,including those listed above, which can be coupled to or may be acomponent of a computer, having computer-readable program code meansembodied therein. The term computer-readable storage medium is notintended to limit the type of physical device and includes types ofstorage devices that do not necessarily store information permanently,including for example, random access memory (RAM). Program instructionsand data stored on a tangible computer-readable storage medium/memory innon-transitory form may further be transmitted by transmission media orsignals such as electrical, electromagnetic, or digital signals, whichmay be conveyed via a communication medium such as a network and/or awireless link.

Computer program instructions embodying the present disclosure may alsobe stored in a computer-readable memory that can direct a computer orother suitable programmable device to function in a particular manner,such that the instructions stored in the computer-readable memoryproduce an article of manufacture, including instruction means, thatimplement the function specified in the description or flowchartblock(s). The computer program instructions embodying the methods of thepresent disclosure may also be loaded onto a computer or otherprogrammable device, including a mobile device, to cause a series ofoperational steps to be performed, e.g., by a processor, on the computeror other programmable device to produce a computer-implemented processsuch that the instructions that execute on the computer or otherprogrammable device provide steps for implementing the functionsspecified in the present disclosure.

One skilled in the art will also appreciate that any databases, systems,or components of the present disclosure may consist of any combinationof databases or components at a single location or at multiplelocations, and which may be accessible remotely via any appropriateconnection via any network (cloud, internet, cellular, LAN, WiFi and soon), and wherein each database or system may also include any of varioussuitable security features, such as firewalls, access codes, encryption,de-encryption, compression, decompression, and/or the like.

The disclosed systems and/or methods may be embodied, at least in part,in application software that may be downloaded, in whole or in part,from either a public or private website or an application store (“appstore”) to a mobile device. In another embodiment, the disclosed systemand method may be included in whole or in part in the mobile devicefirmware, hardware, and/or software.

In another embodiment, the disclosed systems and/or methods may beembodied, in whole or in part, in application software executing withina webserver to provide a web-based interface to the describedfunctionality.

In yet other embodiments, all or part of the disclosed systems and/ormethods may be provided as one or more callable modules, an applicationprogramming interface (e.g., an API), a source library, an objectlibrary, a plug-in or snap-in, a dynamic link library (e.g., DLL), orany software architecture capable of providing the functionalitydisclosed herein.

The present disclosure is directed to a method and system forsynchronizing a camera's date and time metadata with actual, correctdata to quickly locate video footage of interest on the camera. Thepresent disclosure is also directed to a method and system for quicklylocating and synchronizing video footage from a plurality of camerasthat may have viewed activity relevant to an incident underinvestigation.

Currently, there is no known method or system for quickly identifying aplurality of cameras that may have viewed activity relevant to anincident under investigation, and quickly, or simultaneously,synchronizing footage from the plurality of cameras, each of which maybe independently owned and operated. The system and methods of thepresent disclosure are particularly useful to investigators whencanvassing a crime scene.

The term “synchronize” is used herein according to its conventionalmeaning, that is, to cause to agree in time of occurrence, or to assignto the same time. For example, synchronizing a camera or video footagerefers to determining an actual date and time that corresponds to arecorded date and time in the camera's metadata. By “synchronizing” acamera, the camera footage can be properly and accurately cued, usingits recorded metadata, to an actual date and time for viewing footage ofinterest.

The term “camera” as used herein, unless otherwise indicated, refers toan imaging (camera lens) unit viewing a scene together with a recorderand recording media that records and stores the images, referred toherein as “camera footage” or “video footage.” The recorder is operablyconnected to the imaging unit, and the recorder is usually locatedwithin close proximity to the imaging unit.

The term “metadata” is used herein according to its conventional meaningto refer to data that describes and gives information about other data.For example, metadata about recorded video includes a date and timeassociated with, and is usually recorded with, or stored in a video fileassociated with, recorded video footage. Metadata, including date andtime may be superimposed over and simultaneously viewed along with thefootage on a monitor connected to the camera. The date/time recorded inthe metadata advances with the temporally advancing video footage.

Accordingly, “recorded” date and time refers to the recorded date andtime saved as metadata associated with recorded camera footage.

The phrase “actual” is used according to its normal usage to refer toactual, true, date and time. Preferably, an actual date and time as usedherein is obtained from a verifiable and reliable source of date/timedata.

An embodiment of a system of the disclosure is described in reference toFIGS. 19 and 20. Referring to FIG. 19, in one embodiment, a system 200of the present disclosure includes a plurality of user devices 202operatively connected to a database 203. In the embodiments shown, oneor more of the user devices 202 are mobile devices. Such mobile devicesmay be mobile phones, tablets, or other portable programmable devicesconfigured with any suitable networking components for communicating viathe network 206 with the database 203.

In other embodiments, one or more of the user devices 202 may be acomputer system such as desktop or portable laptop computers havingaccess to and configured to execute a canvassing module 208 and othermodules described herein to perform the methods of the presentdisclosure.

The database 203, which may be stored in remote computer storage mediaor in so-called cloud storage 204 and accessed via a suitable network206 connection, is accessible to each one of the user devices 202 viathe canvassing module or app 208 associated with each corresponding userdevice 202. The database 203 is configured to receive and store, andallow access to, details associated with video cameras via thecanvassing modules 208. The details stored in the database 203 includeat least corrections to each of the camera's date/time metadata neededto synchronize the cameras to an actual, correct date/time, and alocation of each of the cameras.

One of skill in the art will appreciate that the user device(s) 202 mayalso include storage and/or cache 205 for storing, either temporarily,or permanently, data retrieved from the database 203.

The stored details may be accessed and used to identify cameras that mayhave captured information and recorded footage relevant to an incidentor crime under investigation, and to synchronize the footage from theidentified video cameras. The footage acquired by the video cameras mayalso be stored in the database 203 for access by users of the app 208.

Access to the stored details and footage may be controlled by anadministrator, who may provide oversight, e.g., set permissions of userson a group basis, wherein each user device 202 is associated with atleast one group. The administrator may access the app 208 via anadministrator panel screen accessible via the app 208 only to those withadministrative privilege, such as those shown in FIGS. 17 and 18, or viaa web-based interface on any computer device.

A host server device 210 may be operably connected to, or may be part ofthe system 200. Preferably, the host server device 210 is operablyconnected to and able to access the database 203, either remotely, e.g.,via the network 206, or through a direct connection, and may also beoperably connected via the cloud or network 206 to the plurality ofdevices 202. In embodiments, the host server 210 is further configuredto be in communication with the canvassing modules 208, and to controlvarious aspects of the system 200, in an administrative oversightcapacity. For example, the host server device 210 may be accessed by theadministrator via a web-based interface to control which user devices202 can have access to the database 203, and may be configured tofurther limit each user's permissions and access to particular files,including the stored details associated with the video cameras andfootage acquired by the video cameras, stored in the database 203, e.g.,on a group basis, wherein each user device 202 is associated with atleast one group. The host server device 210 may also provide access tousers to download the app 208 and preferably hosts a web-based versionof the canvass programming application 208. Users may then access thesame functionality of the app 208 via the web-based version from anydesktop, laptop computer or cellular device (although some of thefeatures, such as automatic location features, will not be useful to aninvestigator accessing the web-based version from a desktop or laptopcomputer that is not located at a scene of a crime or other incidentunder investigation).

An administrator may also generate a directory associated with a casenumber for the investigation, which may be located on the storage media204, and to which particular users, each user being associated with auser identifier (“user ID”) and password, associated with an authorizedgroup and/or with the case number can save details of cameras and camerafootage either via the app 208 or a web-based interface.

In some embodiments, the host server 210 may be associated with a policedepartment or other investigative authority and may be centrally locatedfor appropriate direct access by an authorized person within theinvestigative body.

FIG. 20 depicts a functional block diagram of an embodiment of one ofthe user devices 202. Each device includes at least a processing device212, and memory or computer-readable storage 214 for storage ofinstructions, software, or executable code, which when executed by theprocessing device 212 causes the processing device(s) 212 to perform themethods and/or method steps of the present disclosure. The instructionsmay be implemented in programming steps of software or instructions viathe canvassing app 208, which is installed on the mobile device 202.Such steps may be executed in cooperation with additional modules andcomponents.

For example, the mobile device 202 also preferably includes a data inputinterface module 218 to facilitate user input, which may include keys orvirtual keys 216, and/or a microphone, a graphical user interface module219 for communicating images to a display screen 220 and a camera module221 for communicating with camera 222. The mobile device 202 may alsoinclude additional apps and/or programming modules that may communicateinformation and data to the canvassing module 208, such as a locationmodule 224 providing automatic location data and functions, a date/timestamp module 226 providing automatic actual time data and functions, anda mapping module 228 integrating camera details over a map for accessand viewing functions inter alia.

While certain functions and methods may be described herein as beingimplemented by these various separate modules, it is understood that themodules represent functionality that may be combined or implemented inany number of ways, e.g., integrated into a single app or otherwisedistributed among various apps, or modules, as well as software modules,and hardware components associated with the mobile device 202 and/oranother device, such as the host server 210.

Embodiments of the methods described herein are implemented via the app208 and system shown in FIGS. 19 and 20. FIGS. 21 and 22 describeembodiments of methods of the present disclosure. It is noted that FIGS.21 and 22 are non-limiting examples, and various methods within thescope of the disclosure may include various combinations of variousfunctional blocks, or method steps, represented in these figures, andthat the various method steps do not necessarily have to be performed inthe order indicated in the figures, but may be performed in any suitableorder, and/or simultaneously.

In reference to FIG. 21, embodiments of a method 230 for synchronizingcamera footage from a plurality of cameras includes identifying, at 232,a plurality of cameras that may be relevant to an investigation of anincident that occurred at a predetermined date and time based onlocation data. The method also includes associating a correction, at234, to each of the camera's date and time metadata to synchronizerecorded camera footage to an actual date and time, and then applying,at 236, the correction corresponding to each camera to determine anadjusted date and time in the metadata of the corresponding camera thatcorresponds to footage recorded at the actual, predetermined date andtime of the incident.

Once the user identifies relevant cameras via the app 208, and inembodiments, generates a list, at 240 of, the relevant cameras based onlocation, each correction can be applied across all identified cameras,at 238, to each camera simultaneously to synchronize the plurality ofcameras to an actual predetermined date/time of an incident of interest.In embodiments, once the list of relevant cameras are identified, a newpredetermined time of incident may be entered, if desired, and applied,at 239, to simultaneously determine a new adjusted date and time foreach of the plurality of cameras based on the correction thatcorresponds to each camera. The list, which can also contain any numberof additional details about each camera, as well as investigator's notesand so on, can then be exported, at 242, to any suitable file format,for generating a report, for example, or to an email account, and whichmay be saved by the user, e.g., in a user's directory (a directory towhich the user is granted access, e.g., by case number), in any suitablestorage media. The list may also be associated, at 243, with a casenumber, and/or group associated with the user operating a particularuser device.

In embodiments, the list can be exported to a table listing theplurality of cameras along with their associated details, and saved inany suitable file format. The list/table can be further be associatedwith a case number, and saved in file format to a directory, forexample, associated with the case number. The associated recordedfootage from the cameras in the list may also be stored in thedirectory, to which access may be limited to only those users associatedwith the particular investigation and case number.

While the database 203 may be accessed by users via the canvassing app208 to retrieve camera details, and to calculate the adjusted date/timein metadata to synchronize camera footage, users preferably also add newcameras to continue to build the database 204 via the app 208. Even if auser wishes to access the app 208 for a quick calculation of acorrection to a camera of interest, the user is prompted to at least addthe location of the camera. The user input including the location andthe details required to calculate the correction are automatically addedto the database. The correction is also automatically calculated andstored with the camera details, so that cameras of interest to futureinvestigations can be both quickly identified and synchronized.

Accordingly, referring also to FIG. 22, embodiments of the method mayalso include implementing the app 208 for receiving and storing, at 244,in the database 203, details of cameras including location data, whichcan then be used to quickly identify, at 246, any number of cameras thatare relevant to an investigation based on the location details of allcameras stored in the database 203. The corrections associated with eachof the cameras are calculated, at 248, and each correction, andpreferably the actual date/time and observed date/time relied on forcalculating each of the corrections are also preferably stored, at 249,in the database. This information is valuable for verifying the accuracyof the calculations and for supporting the relevance and veracity of thefootage if needed at trial.

When a user enters location data for a new camera via a mobile device202, presumably the mobile device is, at the time the camera's locationis entered by the user, co-located with the camera. Accordingly, inembodiments, the user may choose an option via the app to automaticallyimport, at 266, the current GPS location for the mobile device to theapp for receiving and storing the camera location in the database 203.

The user may manually add both the observed day and time metadata andthe concurrent actual day and time of the observation. In someembodiments, the app 208 automatically imports, at 250, and saves theactual date and time when the observed metadata is entered. The actualdate/time may be imported from a date/time stamp acquired from thecellular network connected to the mobile device 202, from GPS, or othersuitable sources, and may be processed via the date/time stamp module226. As the details for each of the new cameras are entered via the app208, the correction is automatically calculated, at 248, and preferablystored, at 249, in the database 203 for each camera.

In some embodiments, a user may also take a photo of the observed dateand time displayed on a DVR, e.g., and save it to the user device aswell as to the database 203. The photo acquired by the mobile device 202will also have an automatically-generated time stamp, so that the photoof the DVR metadata together with the actual date and time from themobile device metadata (the automatically-generated time stamp) provideadditional data to verify the accuracy of the corrections calculated foreach camera.

As described further in regard to an example of various screens (FIGS.1-15) and functions of an app formed in accordance with the disclosure,embodiments also include mapping features for, inter alia, quickly andvisually identifying relevant cameras and details. For example,referring still to FIG. 22, embodiments may include generating a map ofan area that includes the incident location, at 252, and displaying iton the user's mobile device 202. The method further includes indicatingthe incident location on the map with a first graphical element, at 254,and populating the map, at 256, with a plurality of second graphicalelements indicating the geographical location of each camera from thedatabase within a selected area around the first graphical element.Accordingly, relevant cameras are easily identified, at 246, as thoselocated within the selected area shown on the map.

In embodiments, a pin may be dragged and dropped, at 264, onto the mapto indicate a location of interest, e.g., the location of the incidentunder investigation.

In additional embodiments, the app 208 preferably allows the uservarious options for selecting the area around the incident foridentifying cameras thought to be relevant. For example, the area may beselected, at 258, as the entire map displayed on the map screen of theuser device 202. In this case, the geographical area used toidentify/view locations of relevant cameras is controlled by the areadisplayed on the map, as selected by the user via a user-adjustablezooming feature toggled to the display, for example. The user may alsoselect the area to be any bounded region graphically defined by userinput via the mobile device, at 260, e.g., by drawing any region ofinterest around the incident location. The user may also select, at 262,an option for selecting a radial distance around the incident locationto locate relevant cameras, and may enter any user-defined distance touse for plotting cameras on the map that fall within that distance fromthe incident.

The list of cameras that are identified as potentially relevant to theinvestigation of the incident may then be generated, at 268, from thosecameras displayed in the selected area of the map. The list of camerasmay be further filtered, at 270, in accordance with any of the fields ofdetails recorded in the database 203.

In further embodiments, the user may also select one or more detailsassociated with the cameras, and superimpose, at 272, the selecteddetails on the map one of the cameras, e.g., by hovering a pointer overthe camera, or simultaneously for all of the cameras, e.g., using atoggle selected via the app 208.

Further embodiments of the methods of the present disclosure implementedvia the canvassing app 208, as accessed and utilized by a user from amobile device 202, will be apparent in further reference touser-viewable screens shown in FIGS. 1-15. It is understood that theparticular design elements used in this example, including displays,screens, and means of moving from one screen to another, or of otherfunctions, by virtual buttons, virtual keyboard strokes and so on can beimplemented in numerous ways and the methods of the disclosure are notlimited thereto.

It is noted that FIGS. 1-15 also refer to a “DVR,” a digital videorecorder, however, it is understood that the scope of the disclosure isnot limited thereto. The methods and systems described herein and in thefigures apply to any type of suitable imaging camera that acquires andrecords serial images or video on either analog or digital recordingmedia, and wherein the recorded serial images or video, both of whichare encompassed in the terms “video footage” and “camera footage,” areassociated with recorded metadata.

It is also noted that the term DVR normally refers only to the recorderthat records the camera footage on digital media. The DVR is operativelyconnected to an imaging (camera lens) unit, also referred to herein asthe “viewing lens” portion of the video camera. It is the viewing lensthat actually views a scene. The term “camera” and “video camera” areused interchangeably herein, unless otherwise indicated, to refer to theentire unit comprising both the viewing lens and the recorder thatrecords and stores the images to video media. The DVR and viewing lensportion are usually located within close proximity to each other, at thesame location.

FIGS. 1-15 assume that the DVR and the viewing lens are at the samelocation. However, in embodiments in which the recording unit or DVR maybe located remotely from the viewing lens, the app 208 is configured toallow a user to enter a location for the viewing lens (which is thelocation used to identify cameras which may have viewed the incident ofinterest) and a different location for the DVR and the recorded footage.Knowing where to retrieve evidentiary footage in such cases will saveinvestigators valuable time.

Referring to FIGS. 1-15, various screens 10 of an exemplary app can beviewed on a display 220 of a mobile device 202. Three main functions ofthe app 208 are preferably directly accessible from most screens, viavirtual buttons, for example, once a user has accessed the app: acalculator button 12, a DVR List button 14, and a Profile button 16.

As shown in FIGS. 1-4, e.g., a user can access and scroll through a“calculator screen” 18 providing the functionality of a date and timecalculator, for example, by pressing the calculator button 12. Thecalculator screen 10 may be accessed to quickly calculate the correction(at 248, FIG. 21, e.g.) and synchronize video footage for a cameraalready in the database, which may be easily identified, e.g., from amap view 106 (see FIG. 13) generated by integrating the camera locationdetails over the map via mapping module 228, e.g., or by entering alocation in box 20, as shown in FIG. 13, or for a new camera not yetstored in the database 203 and to synchronize video footage. If thecamera details are already stored in the database 203, once a userlocates it from a map view 106, and clicks on the camera location, or byadding the location in box 20 directly in the calculator screen 18, allpreviously stored data is automatically loaded into the user screen. Atthis point, upon identifying the camera of interest stored in thedatabase based on location, the app 208 loads all stored details,including the correction, which is loaded into boxes 30 and 32 as adifference in days 30 and hours 34 (see FIG. 3), and the user only needsto enter the date and time of an incident of interest, which the userwishes to locate on the DVR footage, in box 26 (see FIG. 2). Theadjusted date and time may then be automatically calculated in responseto entering the data, or in embodiments, in response to clicking acalculate button 28, and are displayed as the adjusted or “Go To” date,in box 34 and time, in box 36 (FIG. 3).

In embodiments, the user may also access the calculator screen 18, andnot enter any location data—either manually or automatically—andinstead, only enters a current, actual date and time in box 22, theobserved DVR date and time (metadata) in box 24 (see FIG. 1), and theincident date and time in box 26. Upon entering the data, or in responseto clicking the calculate button 28, the correction (boxes 30 and 32)and the adjusted date and time in metadata (boxes 34 and 36) areautomatically calculated and loaded into the appropriate boxes displayedon the calculator screen 18.

As described supra, e.g., in reference to FIG. 22, step 250, inembodiments, the current, actual date and time that coincides with theuser's entering the metadata in box 24 for any camera may beautomatically imported via a date/time stamp acquired, e.g., via a GPSor cellular network or other reliable source accessible to the app 208on the user's mobile device 202.

From the calculator screen 18, the user may also enter an address 20where the camera of interest is located. Optionally, no address isentered and a location is automatically input using geolocation dataretrieved from the mobile device, e.g., via location module 224.

It is noted that for any one or more of the automatic locating andautomatic time/stamp options described herein, an embodiment of the app208 may provide a toggle next to the relevant data box on the screensthat allows either manual entry by the user, or by enabling the toggle,automatically imports current data based on the user device's currentlocation and on the current actual date/time.

Referring again to FIG. 2, which may be viewed by scrolling down thecalculator screen 18, any data may be input by the user via a virtualkeyboard, for example, displayed on the mobile device, including:

-   -   Current Date and Time 22    -   DVR Date and Time 24—the date and time currently shown on the        DVR    -   Incident Date and Time 26—the date and time of the incident to        be located on the DVR footage

Referring to FIG. 3, as describe supra, calculate button 28 may beprovided on the screen 18. In embodiments, in response to the userpressing “calculate” 28, and based on the details 22, 24, 26 input bythe user, the app 208 calculates and displays:

-   -   Difference in Days 30    -   Difference in Hours 32    -   Go to Date 34 (the adjusted date to turn the DVR to, to locate        and view the incident)    -   Go to Time 36 (the time to turn the DVR to, to locate and view        the incident)

In embodiments, the calculation will optionally, or additionally, beautomatically performed and the results 30, 32, 34, 36 automaticallyfilled in on the screen 18, in response to the user properly enteringall the details 22, 24, 26 needed for the calculation by hitting avirtual return or tab key, for example.

Any time the user accesses a camera from the database and updates any ofthe details, and anytime the user adds details for a newly added camera,the app 208 preferably updates the database 203 accordingly, e.g., withthe location of the DVR, and the calculated difference in days 30 andtime 32. The user may also simultaneously add the camera(s) to a userDVR List (see FIG. 10, e.g.), which may also be stored with the database203 in remote storage 204, but which is also preferably associated witha unique user ID and/or a case number so that the user can input andtrack all cameras related to a particular incident, investigation, orcase. The location information and data needed to calculate the adjustedday and time also preferably automatically fill in a DVR Details Screen42 as further described in reference to FIGS. 5-9 below, the entirecontents of which are stored in the database 203.

A reset button 38 may also be provided on the calculator screen 18which, when pressed, resets or clears the details entered by the user aswell as the calculated results.

Once data is entered via the calculator screen 18, as shown in FIGS.4A-4B corresponding to FIGS. 1-2, respectively, calculations arepreformed (as shown in FIG. 4C, corresponding to FIG. 3) for a DVRlocated at an address entered by the user (or obtained automatically viathe mobile device's geolocation capability) to determine the date 34 andtime 36 the user should turn this particular DVR to, to locate and viewthe incident of interest, or relevant information related thereto,assuming the DVR actually captured footage that is useful to the user.

Referring to FIG. 5, on scrolling further down the calculator screen 18in the embodiment shown, the user can add additional useful details forstorage to a DVR Details table and/or database by pressing an “Add DVRDetails” button 40, for example, which accesses and displays an editable“DVR Details” 42 screen. Details can be entered, including but notlimited to: the building name where the DVR is located; further detailsabout DVR location; building phone number; individual contact personname and phone number; DVR make, model, length of time it can record;whether the cameras' viewing lens are interior or exterior; whethercamera is operable; and additional investigator's notes.

FIGS. 6-10 describe several ways a user may enter, edit and viewadditional details for a new or existing camera for storage in thedatabase 203 and in other user-accessible lists, which can then beaccessed for identifying and synchronizing cameras relevant to aparticular investigation.

As shown in FIGS. 6A-6C, an editable DVR Details screen 42 allows theuser to add, as well as edit, information about a particular DVR. Suchinformation can include, but is not limited to, any one or more of thefollowing:

-   -   Name of the location 44 (or a shorthand name could also be        assigned).    -   Location information 46—will preferably automatically plug in        based on address entered on the calculator screen; can also        edit.        -   Phone number 48    -   Contact Information 50 which may include        -   Contact Name 52 and/or        -   Contact Phone Number 54    -   DVR information 56        -   DVR make and model 58        -   Length of time recorded 60 (how long is the video stored on            this DVR)        -   Location 45, if different than the location 46 corresponding            to the viewing lens of the video camera    -   3 check off boxes for future reference 62        -   Camera not operable 64        -   Exterior Cameras 66        -   Interior Cameras 68    -   Date that data was last acquired to synchronize the camera    -   Notes 70: The calculations will preferably automatically plug        into the notes section 70. A user can type in any notes under        the calculations, storing both, or may clear the calculations by        deletion or pressing a “clear” button 72.

When the user has completed entry of data in all the fields relevant tothe information the user wishes to save, as shown for example in FIGS.7A-7C corresponding to FIGS. 6A-6C, respectively, the user can press a“Done” button 74. The editable DVR Details screen 42 also may include(on the top of the screen in this example), a cancel button 76 providingthe option to cancel entry of additional details.

Referring to FIGS. 7A-7C, once the details are saved, by pressing Done74, for example, the DVR information recorded in the fields of theeditable DVR Details screen 42 is automatically displayed on a DVRDetails screen 78, and may also be automatically exported to the user'scurrent DVR List 88 (see FIG. 10, e.g.).

The DVR Details, once saved by selecting “Done” are shown on a saved DVRDetails screen 79, which also includes a Menu button 80. After pressingDone 74, for example, the user may review the saved DVR Detailsinformation for accuracy. If further edits are needed, as shown in FIG.8, the user can press the Menu button 80 to display a Menu screen 82,which in turn provides an Edit option 84 for accessing the editable DVRDetails screen 42. Additional options on the Menu may include, withoutlimitation, adding a calculation 103 (if camera is added anew and thencalculations performed, e.g.), export button 104 to export the DVRDetails to a database; and/or a delete button 105 to delete the DVR.

From the DVR Details screen, there is also an option to “view on map” 85which, when selected by the user, displays a map screen (FIG. 9) showingthe location of the DVR using the location data 46.

Referring to FIG. 10, a DVR List 88 may be displayed by pressing the DVRList button 14, which is accessible from at least the main screensdisplayed by the app.

After a user has completed the DVR details, the DVR information ispreferably automatically stored in the database 203, and to the user'sDVR List 88 of all DVR's a user has ever entered and stored. Inembodiments, the DVR List 88 also includes DVR's entered and stored byother users with whom the user has opted to share the information, orwith other users associated with a group having shared access asdetermined, e.g., by an administrator.

Any one of the DVR's full details may be displayed in the correspondingDVR Details screen 78 for a DVR when the DVR is selected from the List88, by the user touching or pressing a virtual selection button, arrow,or the DVR name, for example. As described supra, the location of theselected DVR 90 can then also be viewed on a map by selecting a “view onmap” button 85, for example, from the completed DVR Details screen 78.

In other embodiments, in addition to the camera details described above,the database 208 may also store for each camera actual views and cameraangles, allowing the user to see the camera coverage of a specific area.Accordingly, when a camera is selected from a DVR List, for example, inaddition to the details, and the map view, a representative camera viewrepresentative of the video coverage is also stored and available forviewing by a user, showing the camera view on a map.

FIGS. 10-16 describe several ways a user may implement an embodiment ofthe app 208 to locate, sort, search, filter, export, and otherwiseaccess the database 203 for quickly identifying, locating andsynchronizing camera footage relevant to a particular investigation.

Referring to FIGS. 10 to 13, in the embodiment shown, the DVR Listscreen 88 includes three options for performing the following additionalfunctionalities: a sort, a search, and a map function via a sort button92, search bar 94 and a map button 96, for example.

To sort the list of DVR's, the sort button 92 is selected by the user.The user may select an option for sorting by, e.g.: the date 98 the DVRwas added, for example, from most recent to the oldest; or by distance100. The sort by distance function 100 may include at least thefollowing options:

-   -   1. Enter no address and the list will sort based on the user's        current location, which may be automatically detected via GPS        location of the user device        -   a. Preferably will list closest location to the user's            current location first; or    -   2. Enter an address in the search bar 94 and select sort by        distance 100        -   a. This will sort the list with all DVR's within a            predetermined distance selected by the user, e.g., a mile of            the location entered.        -   b. The list will preferably sort from the closest to the            location entered, to the furthest.

To search the list of DVR's, identifying information is entered in thesearch bar 94 by the user. The search may be initiated by pressing avirtual return button or pressing a search button 102. For example, theuser may enter text to search by any of the fields of details entered inthe DVR List, including but not limited to:

-   -   Camera Operable    -   Date added/entered    -   Date Last synched    -   Name    -   Address    -   Zip Code    -   Key words        Referring to FIG. 14, the results of any search may be compiled        in a list and exported, in embodiments, by selecting the Menu        option 80 to open the Menu 82 and then the export button 104.

Referring also to FIG. 22, embodiments of the method of the disclosuremay be implemented via the mapping functionality via the user device 202to assist the user in quickly identifying relevant cameras based ontheir location relevant to the incident. When the user elects the mapbutton 96 from the DVR List screen 88, a map is generated on a mapscreen 106 (FIG. 13) of the user's current location 108 as well as thelocation of all the DVR's 112 in the DVR List within the displayed maparea. The current location may be automatically filled in on a text bar110 from the most recent data entered by the user, or automaticallyfilled in from geolocation data provided by the mobile device.

In addition, any location, such as a location relevant to an incident ofinterest, may be filled in manually in a search text bar 114 in order toidentify DVR's around the location entered in the text bar 114 which mayhave captured relevant footage, and to view the DVR's on the map.Accordingly, the method includes generating, at 252, via the app, a mapof an area that includes the incident location, and displaying the map,at 252, on the user device, which is operatively connected to thedatabase. The method further includes populating the map, at 256, withgraphical elements, such as pins, indicating the locations of camerasfrom the database that are located within a selected area around theincident location. In yet another embodiment, a pin may be dragged anddropped by the user, at 264, onto the location of interest; the closestaddress is then used to fill in box 114. The cameras identified as beingrelevant, based on their location to the location relevant to theincident, indicated in box 114 and on the map 106, may include allcameras that are located within the area displayed on the map, at 258,or may be an area selected in accordance with a user-defined distance,at 262, from the incident location 114 that can be entered (box notshown), e.g., via either the map screen 106 or sorting screen (FIG. 1).In other embodiments, the cameras identified for synchronizing andexamining footage are those within a bounded region, which is “drawn” bythe user, at 260, on the map via the display in the user device.

A graphical element is also used, at 254, to indicate the location ofinterest, e.g., the incident location on the map. In embodiments,different graphical elements may be used, at 256, to differentiate thelocation of the incident, for example, from the location of cameraswithin a user-selected area around the incident. The graphical elementsmay be the same type of graphical element but differentiated by color,and/or may be different symbols or shapes, for example. The DVR's may bemarked by “pegs” or circles shown on the map and may be color-coded. Forexample, a blue peg could be used to view the current location, a greenpeg could be used to view the location of interest entered in the searchbar, and red pegs may be used to show the location of the DVR's relativeto the current location 108 or to the location manually entered in thesearch bar 114.

In embodiments, any of the details associated with the cameras may alsobe displayed, for example, superimposed on, or highlighted on the mapscreens for each camera indicated on the map. In other embodiments, themap screen 106 may display any one or more of the details associatedwith the DVR's 112 in the DVR List, without leaving the map view, whenthe user hovers over one of the pegs marking the location of aparticular DVR, for example. In another embodiment, the user can selectan option to only show, or to highlight, DVR's from the DVR List in themap view that meet some additional criteria. For example, inembodiments, the user can elect to omit from the map view those camerasthat are currently flagged as not operable (see FIG. 6B, Camera NotOperable Toggle 64). Identifying cameras that are not operable willexpedite the investigation, and not waste time looking for unreliablefootage.

In other embodiments, the DVR's identified in accordance with any of theuser-selected location criteria in relation to the location of theincident (in box 114, e.g.) described herein using the map functionalityof the app 208 may be exported into a list of DVR's associated with theparticular incident or case. The list may be filtered according to anyof the details of the cameras stored in the database. In addition,toggles such as “camera inoperable” may be visibly highlighted in anysuitable graphical form, to flag on the map, which of the identifiedcameras will not have any reliable evidence and need not be pursued.

In additional embodiments, the map screens are integrated with GOOGLE®earth so that images of the actual locations (“street views”) of thecameras in the DVR List can also be seen.

Referring to FIGS. 14-16, the user can export the entire DVR Listavailable, or any filtered list, e.g., the list of cameras identifiedbased on their relative location to the location of the incident ofinterest (which may be determined via the mapping functions describedsupra), by selecting an export button 104 from the Menu screen 82.Another naming screen 116 may be displayed when the export button 104 isselected to allow the user to enter a file name 118 for a report, whichmay be in excel format, for example, comprising the DVR List. The reportcan then be emailed to an account on file for the user, printed, and/orsaved. An example of the report that may be generated is provided inFIG. 16. Preferably, the report is generated in an excel format or othersearchable and sortable file type, and, referring also to FIGS. 1-3, and6A-6C, contains all entered data and automatically imported data,including location name 44 and address 46 of the camera, contact detailssuch as contact name 52, contact telephone number 54, camera detailssuch as make and model 56, length of time recorded 60, and status 64(operable or not) and whether there are exterior cameras 66 and/orinterior cameras 68 at that location 46 and all entered and calculateddata 55 (current date and time 22: DVR Date and Time shown 24:calculated difference in days 30 and hours 32) needed to properly locatefootage recorded on each camera corresponding to an actual date and timeof an incident 26, along with the adjusted date 34 and time 36 to turnthe DVR to, to locate and view the incident occurring at the actual dateand time 26. FIG. 16 is one example of a report. Reports may becustomized by the user to include any selected details for each camerain a list, or filtered list.

In various embodiments, a user may log in to an app or to a websiteproviding the functionality described herein. Upon purchase of the appor access to the website, the user provides identifying information toset up a login account, which may be password-protected. The identifyinginformation may also be used to perform various administrativefunctions, particularly related to building a database of the cameradata input by users and the calculations generated by the program. Thedata may be made accessible to users based on read/write privilegesassociated with each camera, and on membership of a user requestingaccess in a particular group. For example, all data entered for allcameras in the database may be made available to any user logging in asa member of a group associated with a particular law enforcement agency.In another example, users may be part of a community watch group havingaccess only to camera data that is input by members of the communitywatch group.

The database 203 corresponding to the DVR list associated with any suchgroup is preferably accessible via the internet to users having theprerequisite privilege, and may be maintained in the cloud, such thateach user can share his/her list to others, if authorized. An option maybe provided to subscribe to the list/directory based on area (by zipcode or city/state or neighborhood, and so on).

A user may be prompted on first use of the app or program to enter alogin name or other identifier (ID), which may be an email address, forexample, and then to enter a password for access to the app anddatabase. Identifying information may include:

-   -   First Name    -   Last Name    -   Email Password    -   Location: City, State, Zip Code    -   Occupation    -   Agency    -   Phone Number (Optional)

FIGS. 17 and 18 provide examples of screens through which variousadministrative functions are made available to an administrator of theusers and database associated with the app. An administrator panel ofusers 120 is shown in FIG. 17, from which the administrator can view alist of all users by any of the various identifying information, suchoccupation, agency (which may be used to set group access privileges),location, email address, and phone number. Functions are provided tosearch 122 by any keyword or other criteria and to export 124 the entirelist, or the filtered list associated with the search criteria orkeyword, if entered. The list may be in excel or any other suitable fileformat, such as a PDF file, or word file, rtf, and so on. An uploadfunction 126 may also be provided to allow the administrator to uploadthe entire or filtered list to a user's account.

An administrator panel of DVR's 130 in a DVR List is shown in FIG. 18,from which the administrator can view a list of all DVR's (or othercameras) for which data has been entered by all users of the app orwebsite service, or by any selected group of users associated with agroup, and which may be exported by selecting an export button 132, forexample, in full, or filtered be any search criteria or keyword enteredin the search bar 134. The exported list of DVR's may be in excel or anyother suitable file format, such as a PDF file, or word file, rtf, andso on. The list, like the other lists and reports that can be generatedby the app, may be sent directly to an administrator email account, orto a user email account selected by the administrator, and may also beprinted and/or saved.

The exported list of all DVR's preferably contains the user name or IDof the user who entered the DVR and the date the record was created bythe user, and also preferably contains all of the details entered byusers and generated by the app, including:

-   -   Location name, address, phone #    -   Contact name, and phone #    -   Operable, exterior, or interior cameras    -   Make/model, length of time recorded

In additional embodiments, a file, such as a .csv file, containingproperly formatted records of DVR data can be uploaded into the database203 associated with the app or program or into any other database, andmay be further identified with a case number or other identifier tolimit access.

In additional embodiments, the method may include options to tailor theuse of the app (or other software program implementing the method of thedisclosure) to a particular group, such as law enforcement. Accordingly,additional options may be provided to: enter case numbers; enterphotographs, for example, of a street or sidewalk view, or other cameraviews from the DVR. Additional options may include to: upload DVR Listand/or Details, and/or video footage taken from selected DVR's to adirectory, which may be in the cloud.

In embodiments, the video footage saved for an identified list ofcameras identified as relevant to an incident, based on location, may beautomatically and, optionally, simultaneously cued using the correctionto the metadata, to the actual date and time of the incident. In variousembodiments, the synchronized footage from several cameras may bedisplayed side-by-side on a single monitor for comparison.

Various embodiments may include adding more details saved for thecameras in the List and database. For example, instructions on how todownload video from the listed DVR may be included.

The system and methods provided herein advantageously reduce the risk ofmissing vital camera footage during a canvass of a crime scene, reducehuman error that would otherwise occur in calculating and manuallyentering corrected date/time data, generated verifiable documentationfor use at trial, significantly reduces investigative time in gatheringand reviewing evidence, particularly in locating relevant and reliablecamera footage, and assists in developing new leads with targeteddeployment.

Particular embodiments of the present disclosure have been describedherein, however, it is to be understood that the disclosed embodimentsare merely examples of the disclosure, which may be embodied in variousforms. Well-known functions or constructions are not described in detailto avoid obscuring the present disclosure in unnecessary detail.Therefore, specific structural and functional details disclosed hereinare not to be interpreted as limiting, but merely as a basis for theclaims and as a representative basis for teaching one skilled in the artto variously employ the present disclosure in any appropriately detailedstructure.

What is claimed is:
 1. A method for synchronizing camera footage from aplurality of cameras, the method comprising: identifying, by aprocessing device, from a database of cameras, a plurality of camerasthat are associated with an incident, based at least on a location ofeach of the plurality of cameras; associating, by the processing device,each of the plurality of cameras with a correction to at least one of adate and a time in metadata associated with footage recorded by thecorresponding camera to facilitate synchronization of the footagerecorded by each of the plurality of cameras to an actual date and time,and storing the correction to the metadata for each of the plurality ofcameras in the database; applying, by the processing device, thecorrection stored in the database associated with each of the pluralityof cameras to determine at least one of an adjusted date and an adjustedtime in the metadata for each of the plurality of cameras correspondingto footage recorded at a particular date and time related to theincident; and synchronizing the footage of each of the plurality ofcameras to the particular date and time, including cueing the footage ofeach of the plurality of cameras to the particular date and time basedon the at least one of the adjusted date and the adjusted timedetermined from the correction to the metadata stored in the databasefor each of the plurality of cameras.
 2. The method of claim 1, whereinapplying includes simultaneously applying the correction to the metadatastored in the database for each of the plurality of cameras.
 3. Themethod of claim 1, further comprising: generating, by the processingdevice, a list of the plurality of cameras identified from theidentifying step, wherein the list includes the location, thecorrection, and the at least one of the adjusted date and the adjustedtime in the metadata associated with each of the plurality of cameras;and exporting, by the processing device, the list to at least one of afile and an email account associated with a user ID.
 4. The method ofclaim 1, the method further including: receiving and storing, by aprocessing device, details of cameras, including the plurality ofcameras, in the database of cameras, the details including locationdetails including a geographical location associated with each camera inthe database, and wherein identifying includes identifying the pluralityof cameras from the location details stored in the database based on thelocation of each of the plurality of cameras relative to an incidentlocation at which the incident occurred.
 5. The method of claim 4,wherein the details received and stored for one camera in the databaseof cameras include the actual date and time and at least one of anobserved date and an observed time in the metadata coinciding with theactual date and time, wherein the at least one of the observed date andthe observed time are received via user input to a user deviceoperatively connected to the database, the method further including:calculating, for the one camera, the correction to the metadata tosynchronize the footage for the one camera based on the at least one ofthe observed date and the observed time recorded by the one cameracoinciding with the actual date and time; and associating the one camerawith the corresponding correction and storing the correspondingcorrection in the database.
 6. The method of claim 5, wherein the actualdate and time for the one camera is automatically imported via the userdevice from one of a cellular network and a GPS date/time stampcoinciding with the observed date and the observed time in the metadata.7. The method of claim 4, the method further comprising: generating amap of an area that includes the incident location, and displaying it ona user device operatively connected to the database; and indicating theincident location on the map with a first graphical element; and whereinidentifying the plurality of cameras based on the location of each ofthe plurality of cameras relative to the incident location furtherincludes: populating the map with a plurality of second graphicalelements indicating the geographical location of each camera from thedatabase within a selected area around the first graphical element, eachcamera located within the selected area corresponding to one of theplurality of cameras.
 8. The method of claim 7, wherein the selectedarea is the area of the map displayed on the user device.
 9. The methodof claim 7, wherein the selected area is a bounded region graphicallydefined by user input via the user device.
 10. The method of claim 9,wherein the bounded region is defined by a user-defined distance fromthe incident location.
 11. The method of claim 7, wherein indicating theincident location includes fixing the first graphical element inresponse to user input that includes dragging and dropping the firstgraphical element to the incident location on the map.
 12. The method ofclaim 4, wherein receiving and storing further includes automaticallyimporting the geographical location for one of the cameras co-locatedwith a user device based on GPS location data for the user device. 13.The method of claim 7, further comprising generating a list of theplurality of cameras corresponding to the plurality of second graphicalelements within the selected area, wherein the list includes at leastthe location and the correction associated with each of the plurality ofcameras, and the at least one of the adjusted date and the adjusted timein the metadata associated with each of the plurality of cameras. 14.The method of claim 1, further comprising receiving, via user input to auser device operatively connected to the processing device, a newparticular date and time and simultaneously determining at least one ofa new adjusted date and a new adjusted time for one of the plurality ofcameras based on the correction stored in the database for the one ofthe plurality of cameras.
 15. The method of claim 7, further comprisingselecting, via user input, one or more details associated with each ofthe plurality of cameras, and superimposing on the map the one or moredetails for at least one of the plurality of cameras.
 16. The method ofclaim 13, further comprising filtering the list according to any of thedetails of the cameras stored in the database, and graphicallyhighlighting the filtered list on the map.
 17. The method of claim 4,wherein the details of each of the cameras in the database furtherinclude at least one of a camera operable indicator, the flag indicatingone of operable and not operable status, contact information, a make andmodel of the corresponding camera, a date the corresponding camera wasentered into the database, and a date the corresponding camera was lastsynchronized.
 18. The method of claim 3, the method further comprisingassociating, by the processing device, the list with at least one of acase number, a user ID, and a group associated with the user ID.
 19. Themethod of claim 1, wherein the identifying further includes identifyingthe plurality of cameras that are associated with the incident that areoperable, based on the location of each of the plurality of cameras andon a flag associated with and stored in the database for each of theplurality of cameras, the flag indicating one of operable and notoperable status.